High-efficiency wireless local-area network devices and methods for acknowledgements during scheduled transmission opportunities

ABSTRACT

Embodiments of a system and method for acknowledging frames in a wireless network are generally described herein. In some embodiments, a wireless communication device may include a transmit/receive unit configured to receive data from a sender. In some embodiments, the transmit/receive unit may be configured to receive a schedule. The transmit/receive unit may be further configured to acknowledge (ACK) the data in a first scheduled transmission to the sender. The first scheduled transmission to the sender may be determined based on the schedule. In some embodiments, the acknowledgement may be an acknowledgement frame or a block acknowledgment frame. The scheduled transmission to the sender may be determined based on the schedule.

PRIORITY CLAIM.

This application is a continuation of U.S. patent application Ser. No.14/563,406, filed Dec. 8, 2014, which claims the benefit of priorityunder 35 USC 119(e) to U.S. Provisional Patent Application Ser. No.62/024,813, filed Jul. 15, 2014 [reference number P70598Z], each ofwhich is incorporated herein by reference in its entirety.

TECHNICAL FIELD

Some embodiments described herein generally relate to acknowledgementpolicies in wireless local-area networks (WLANs), some embodimentsgenerally relate to acknowledgement policies for high-efficiencywireless communications including high-efficiency WLAN andhigh-efficiency wireless (HEW) communications, and some embodimentsrelate to acknowledgement policies in 802.11ax.

BACKGROUND

One issue with communicating data over a wireless network isacknowledging received packets. Often acknowledging received packetsconsumes bandwidth.

Thus, there are general needs for systems and methods that reducesignaling, bandwidth and/or delay associated with communicatingacknowledgments of packets.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 illustrates a wireless network in accordance with someembodiments;

FIG. 2 is a method of acknowledgment in 802.11 in accordance withexample embodiments;

FIG. 3 is a method of acknowledgment in 802.11 in accordance withexample embodiments;

FIG. 4 is a method of acknowledgment in 802.11 in accordance withexample embodiments;

FIG. 5 illustrates a schematic diagram of a packet, according to exampleembodiments; and

FIG. 6 illustrates a HEW device in accordance with some embodiments.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1 illustrates a wireless network in accordance with someembodiments. The wireless network may comprise a basis service set (BSS)100 that may include an access point (AP) 102, a plurality of HEWdevices 104 and a plurality of legacy devices 106.

The AP 102 may be an access point (AP) using the Institute of Electricaland Electronics Engineers (IEEE) 802.111 to transmit and receive. Inexample embodiments, the AP 102 may be a base station. The AP 102 mayuse other communications protocols as well as the 802.111 protocol. Forexample the AP 102 may use 802.16 or 802.15.1. The 802.11 protocol maybe 80211ax. The 802.11 protocol may include using OrthogonalFrequency-Division Multiple Access (OFDMA) and/or Space-DivisionMultiple Access (SDMA). The 802.11 may include using multi-usermultiple-input and multiple-output (MU-MIMO). The HEW devices 104 mayoperate in accordance with 802.111ax. The legacy devices 106 may operatein accordance with one or more of 802.11 a/g/ag/n/ac, or another legacywireless communication standard. In example embodiments, the BSS 100 mayinclude more than one AP 102.

The HEW devices 104 may be wireless transmit and receive devices such ascellular telephone, handheld wireless device, wireless glasses, wirelesswatch, wireless personal device, tablet, or another device that may betransmitting and receiving using the 802.11 protocol such as 802.11ax oranother wireless protocol.

The BSS 100 may operate on a primary channel and one or more secondarychannels or sub-channels. The BSS 100 may include one or more APs 102.In accordance with embodiments, the AP 102 may communicate with one ormore of the HEW devices 104 on one or more of the secondary channels orsub-channels or the primary channel. In example embodiments, the AP 102communicates with the legacy devices 106 on the primary channel. Inexample embodiments, the AP 102 may be configured to communicateconcurrently with one or more of the HEW devices 104 on one or more ofthe secondary channels and a legacy device 106 utilizing only theprimary channel and not utilizing any of the secondary channels.

The AP 102 may communicate with legacy devices 106 in accordance withlegacy IEEE 802.11 communication techniques. In example embodiments, theAP 102 may also be configured to communicate with HEW devices 104 inaccordance with legacy IEEE 802.11 communication techniques. Legacy IEEE802.11 communication techniques may refer to any IEEE 802.11communication technique prior to IEEE 802.11ax.

In some embodiments, HEW frames may be configurable to have the samebandwidth or different bandwidths, and the bandwidth may be one of 20MHz, 40 MHz, or 80 MHz contiguous bandwidths or an 80+80 MHz (160 MHz)non-contiguous bandwidth, or another bandwidth. In some embodiments, a320 MHz, contiguous bandwidth may be used. In some embodiments,bandwidths of 1 MHz, 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or anotherbandwidth, or a combination thereof may also be used. In theseembodiments, a HEW frame may be configured for transmitting a number ofspatial streams.

In other embodiments, the AP 102, HEW device 104, and/or legacy device106 may implement one or more of different technologies such ascode-division multiple-access (CDMA) 2000, CDMA2000 1X, CDMA2000evolution data-optimized (EV-DO), Interim Standard 2000 (IS 2000),Interim Standard 95 (IS-95), Interim Standard 856 (1S-856), GlobalSystem for Mobile communications (GSM), Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GUAM, Long-Term Evolution (LTE), 802.15.1,and IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access(WiMAX)).

In an OFDMA system such as 802.11 ax, an associated HEN device 104 mayoperate on different 20 MHz sub-channel of the BSS 100. For example, theBSS 100 may operate on a 80 MHz bandwidth with four subchannels of 20MHz each.

In example embodiments, an AP 102, HEW devices 104, and legacy devices106 use carrier sense multiple access/collision avoidance (CSMA/CA) Insome embodiments, the media access control (MAC) 606 layer (see FIG. 6)controls access to the wireless media.

In example embodiments, an AP 102, HEW devices 104, legacy devices 106,perform carrier sensing and can detect whether or not the channel isfree. For example, an AP 102, HEW device 104, or legacy device 106 mayuse clear channel assessment (CCA) which may include a determinationwhether or not the channel is clear based on a Decibel-milliwatts (dBm)level of reception. In example embodiments, the physical layer (PHY) 604(FIG. 6) is configured to determine a CCA for an AP 102, HEW devices104, and legacy devices 106.

In example embodiments, an AP 102, HEW devices 104, legacy devices 106,access the channel in different ways. For example, in accordance withsome IEEE 802.11ax embodiments, an AP 102 may operate as a masterstation which may be arranged to contend for a wireless medium (e.g.,during a contention period) to receive exclusive control of the mediumfor an HEW control period (i.e., a transmission opportunity (TXOP)). TheAP 102 may transmit an HEW master-sync transmission at the beginning ofthe HEW control period. During the HEW control period, HEW devices 104may communicate with the AP 102 in accordance with a non-contentionbased multiple access technique. This is unlike conventional 802.11communications in which legacy devices 106 and, optionally, HEW devices104 communicate in accordance with a contention-based communicationtechnique, rather than a multiple access technique. During the HEWcontrol period, the AP 102 may communicate with HEW devices 104 usingone or more HEW frames. During the HEW control period, legacy devices106 refrain from communicating. In some embodiments, the master-synctransmission may be referred to as an HEW control and scheduletransmission.

In some embodiments, the multiple-access technique used during the HEWcontrol period may be a scheduled OFDMA technique, although this is nota requirement. In some embodiments, the multiple access technique may bea time-division multiple access (TDMA) technique or a frequency divisionmultiple access (FDMA) technique. In some embodiments, the multipleaccess technique may be a space-division multiple access (SDMA)technique.

The AP 102 may also communicate with legacy devices 106 in accordancewith legacy IEEE 802.11 communication techniques. In some embodiments,the master station may also be configured to communicate with HEWstations outside the HEW control period in accordance with legacy IEEE802.11 communication techniques, although this is not a requirement. HEWdevices 104 may be termed HE (high-efficiency) devices. HEW devices 104may be also/alternatively termed high-efficiency Wi-Fi® (HEW) devices.

In example embodiments, the HEW device 104 and AP 102 are configured toperform one or more of the functions and/or methods described herein foracknowledgements and block acknowledgements such as the methods,apparatuses, and functions described in conjunction with FIGS. 2 through4, and in relation to packet 500.

FIG. 2 is a method 200 of acknowledgment in 802.11 in accordance withexample embodiments. Illustrated in FIG. 2 is time 266 along thehorizontal axis and along the vertical axis are AP 102 HEW device 104.1HEW device 104.2, and legacy device 106. In example embodiments, theremay be one or more HEW devices 104.1, 104.2, one or more APs 102, andone or more legacy devices 106.

In example embodiments, the method 200 begins with the AP 102transmitting during a contention period 201. The AP 102 contends for thewireless medium with other wireless devices: HEW device 104.1, HEWdevice 104.2, and legacy device 106. At the end of the contention period201, the AP 102 has determined that the wireless medium may be free anddetermines to transmit. In each of the method operations, the AP 102 maytransmit according to OFDMA, SDMA, and/or MU-MIMO.

The method 200 continues with the AP 102 transmitting the schedule (SCH)202 to HEW device 104.1, HEW device 104.2, and legacy device 106 asshown by arrows 250.1, 250.2, 270. In example embodiments, the SCH 202may include a legacy header that the legacy device 106 can decode. Inexample embodiments, the SCH 202 includes an indication for how long thelegacy device 106 should set a network allocation vector (NAV), whichindicates how long not to try to access the wireless medium. In exampleembodiments, the legacy device 106 sets the NAV 271 based on a receivedlegacy header from the AP 102. In example embodiments, the SCH 202 is anindication of a stream and time when a HEW device 104 is scheduled foruplink transmission. In example embodiments, the SCH 202 may be aseparate packet. In example embodiments, the schedule (SCH) 202 isincluded in a SIG 204 packet, a management packet such as a beacon orany appropriate packet that is transmitted from the AP 102 to the HEWdevices 104.1, 104.2. In example embodiments, the SCH 202 includes aschedule for two or more HEW devices 104.1, 104.2. In exampleembodiments, the SCH 202 includes a schedule for only one HEW device104.1, 104.2. In some embodiments, the SCH 202 may indicate when the AP102 is scheduled to transmit and receive. In example embodiments, theSCH 202 is configured according to one or more standards such as802.11ax.

In example embodiments, the SCH 202 includes a schedule for both HEWdevice 104.1 and HEW device 104.2. In example embodiments, the AP 102transmits simultaneously a separate SCH 202 to each HEW device 104.1,104.2 as shown by arrows 250.1, 250.2. For example, the AP 102 maytransmit on one sub-channel a first SCH (not illustrated), andsimultaneously transmit on a second sub-channel a second SCH (notillustrated). In example embodiments, the AP 102 may transmit on onespatial stream a first SCH, and simultaneously transmit on a secondsub-channel a second SCH. In example embodiments, the SIG 204 is part ofa Physical Layer Convergence Procedure (PLCP) Packet Protocol Data Unit(PPDU). In example embodiments, the PPDU may be a multi-user (MU) PPDU.

In example embodiments, one or more of the SCH 202, SIG 204, BA 206,DATA 208, a MAC field, or another frame may indicate a policy foracknowledgement such as a beacon frame or probe response frame. Inexample embodiments, the policy for acknowledgement may be per PPDUbasis. In example embodiments, the policy for acknowledgement mayindicate that the block acknowledgement (BA) 210, 214 is to he used in anext scheduled MU-PPDU. In example embodiments, the policy foracknowledgement may be pre-setup by the AP 102 and HEW devices 104.1,104.2 exchanging a new MAC management frame. For example, an ACK setupmanagement frame for MU transmission may be either unicast or multicastand may carry an acknowledgement policy for multiple HEW devices 104and/or APs 102.

The AP 102 may, in some example embodiments, announce a newacknowledgement policy in a beacon or probe. The acknowledgement policymay be for data and/or management frames. There may be more than one AP102. There may be only one HEW device 104.1, 104.2 or more than two, andthere may be more than one legacy device 106.

The method 200 continues with the AP 102 transmitting a SIG 204 to theHEW devices 104.1 104.2 as shown by arrows 250.3, 250.4. In exampleembodiments, the SIG 204 may be a signal field that includes informationregarding the transmission such as a data rate or other information thatmay indicate information regarding the transmission and/or the AP 102.In example embodiments, the AP 102 transmits the same SIG 204 to the HEWdevices 104.1, 104.2. In example embodiments, the AP 102 transmitsdifferent SIGs 204 to the HEW devices 104.1, 104.2.

In example embodiments, the AP 102 transmits the SIG 204 according to astandard such as 802.11ax. In example embodiments, the SIG 204 is partof a management frame. In example embodiments, the SIG 204 is part of aPhysical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU).The PPDU may be a multi-user PPDU.

Optionally, in example embodiments, the method 200 continues with the AP102 transmitting BA 206.1 and BA 206.2 to HEW device 104.1 and HEWdevice 104.2 as shown by arrows 250.5, 250.6, respectively. The AP 102may transmit the BAs 206 simultaneously. The AP 102 may transmit the BAs206 on different frequencies for MU or may transmit the BAs 206 usingspatial diversity on the same frequency. In example embodiments, the BAs206 are block acknowledgements (BA) that acknowledge previouslytransmitted data from the HEW devices 104.1, 104.2.

The method 200 continues with the AP 102 transmitting data 208.1, 208.2as shown by arrows 250.7, 250.8, respectively. In example embodimentsthe AP 102 transmits (arrows 250.7, 250.8) the data 208.1 and data 208.2simultaneously. The data 208.1 and data 208.2 may be data intended forHEW device 104.1 and HEW device 104.2, respectively.

The method 200 continues with HEW device 104.1 and HEW device 104.2transmitting BA 210 and BA 214 as shown by arrows 252.1, 252.2,respectively. As illustrated, HEW device 104.1 may have received SCH202, SIG 204, BA 206.1, and data 208.1, and HEW device 104.2 may havereceived SCH 202. SIG 204, BA 206.2, and data 208.2.

In example embodiments, BAs 210, 214 are block acknowledgements of thedata 208.1, 208.2, respectively. In example embodiments, the BAs 210,214 are to be returned in the first scheduled multi-user Physical LayerConvergence Procedure (PLCP) Physical Data Unit (MU-PPDU) from HEWdevice 104.1 and HEW device 104.2, respectively. In example embodiments,if only one packet was transmitted by the AP 102, then an acknowledgmentor block acknowledgment may be transmitted by the HEW devices 104. Inexample embodiments, an acknowledgment may refer to both anacknowledgment frame and block acknowledgment frame. In exampleembodiments, a previous packet from the AP 102 indicates that the data208.1, 208.2 are to be block acknowledged as part of the next multi-userMU-PPDU from the HEW device 104.1 and HEW device 104.2, respectively. Insome embodiments, an acknowledgement policy indicates that the blockacknowledgement may be part of a subsequent transmission such as thesecond MU-PPDU.

In some embodiments, the BA 210 and BA 214 are transmitted based on aschedule received from the AP 102. In example embodiments, the HEWdevices 104.1, 104.2 do not wait as part of a contention period. Inexample embodiments, the HEW devices 104.1 104.2 begin transmitting inaccordance with a schedule.

Optionally, the method 200 continues with the HEW devices 104.1, 104.2transmitting data 212, 216 as shown by arrows 252.3, 252.4,respectively. In some embodiments, the data 212, 216 are transmitted aspart of a schedule during an up-link period for the HEW devices 104.1,104.2 that may be OFDMA and/or MU-MIMO. In example embodiments, the data212, 216 are transmitted simultaneously. The size of data 212, 216 maybe different. In example embodiments, the BA 210 and BA 214 may be partof the data 212, 216 respectively. In example embodiments, the BAs 210,214 and data 212, 216 may be reversed. In example embodiments, the HEWdevices 104.1, 104.2 transmit additional packets such as a managementpacket such as a probe request or response.

A transmit opportunity (TXOP) 260 may end. The TXOP 260 may be a periodset by the AP 102 in a MAC packet that indicates how long other wirelessdevice such as legacy device 106 should defer accessing the wirelessmedium before attempting to transmit again. The TXOP 260 may include aduration for the HEW devices 104 to transmit an acknowledgment.

Optionally, the method 200 continues with the AP 102 transmitting duringa contention period 217. The AP 102 contends for the wireless mediumwith other wireless devices: HEW device 104.1, HEW device 104.2, andlegacy device 106. At the end of the contention period 217 the AP 102has determined that the wireless medium may be free and determines totransmit. During the contention period 217 other wireless communicationdevices such as APs 102, HEW devices 104, and legacy devices 106 mayhave used the wireless medium.

Optionally, the method 200 continues with the AP 102 transmittingschedule (SCH) 218 to HEW device 104.1 and HEW device 104.2 as shown byarrows 254.1, 254.2, respectively. The TXOP 264 may be similar or thesame as a TXOP 260 as described above. In example embodiments, the SCH218 is a schedule as described for SCH 202. The legacy device 106 mayset NAV 273 in a similar fashion as NAV 271 is set.

Optionally, the method 200 continues with the AP 102 transmitting a SIG220 to the HEW devices 104.1, 104.2 as shown by arrows 254.3, 254.4. Inexample embodiments, the SIG 220 is a signal field as described for SIG204.

Optionally, the method 200 continues with the AP 102 transmitting BAs222.1, 222.2 to HEW device 104.1 and HEW device 104.2 as shown by arrows254.5, 254.6, respectively. In example embodiments the BAs 222.1, 222.2are block acknowledges of the data 212, 216, respectively. In exampleembodiments, the BAs 222.1, 222.2 are transmitted after the data 224.

Optionally, the method 200 continues with the AP 102 transmitting data224.1, 224.2 as shown by arrows 254.7, 254.8, respectively. In exampleembodiments, the data 224.1, 224.2 is data as described for data 208.

Optionally, the method 200 continues with the HEW devices 104.1, 104.2transmitting BAs 226, 230 as shown by arrows 256.1, 256.2, respectively,to the AP 102. The BAs 226, 230 may be block acknowledgements asdescribed for BAs 210, 214.

Optionally, the method 200 continues with the HEW devices 104.1, 104.2transmitting data 228, 240 as shown by arrows 256.3. 256.4,respectively, to the AP 102. In example embodiments, the data 228, 240may he data as described for data 212, 216. The method 200 may end.

FIG. 3 is a method 300 of acknowledgment in 802.11 in accordance withexample embodiments. Illustrated in FIG. 3 is time 366 along thehorizontal axis and along the vertical axis are AP 102, HEW device 104.1HEW device 104.2, and legacy device 106.

In example embodiments, the method 300 begins with the AP 102transmitting during a contention period 301. The AP 102 contends for thewireless medium with other wireless devices such as HEW device 104.1,HEW device 104.2, and legacy device 106. At the end of the contentionperiod 301 the AP 102 has determined that the wireless medium may befree and determines to transmit. In each of the method operations, theAP 102 may transmit according to OFDMA, SDMA, and/or MU-MIMO.

The method 300 continues with the AP 102 transmitting schedule (SCH) 302to HEW device 104.1, HEW device 104.2, and legacy device 106 as shown byarrows 350.1, 350.2, 370, respectively. The SCH 302 may be transmittedseparately on different bandwidths or spatial streams and/or the SCH 302may be transmitted on a primary channel so that the legacy device 106will receive the SCH 302.

In example embodiments, the SCH 302 may be a schedule as described forSCH 202 (FIG. 2). The legacy device 106 may set a NAV 371 based on alegacy header that indicates how long the wireless medium will be usedby the AP 102. The period of time the AP 102 has reserved may be calleda TXOP 360.

The method 300 continues with the AP 102 transmitting SIG 304 to the HEWdevice 104.1 and HEW device 104.2 as shown by arrows 350.3, 350.4,respectively. The SIG 304 may be a signal as described for SIG 204 (FIG.2).

The method 300 continues with the AP 102 transmitting management frames(MGMT) frames 308.1. 308.2 as shown by arrows 350.5, 350.6,respectively. The MGMT frames 308.1, 308.2 may be management frames suchas probe responses and probe requests. In example embodiments, the AP102 may transmit additional packets either before or after the MGMTframes 308.1, 308,2.

The method 300 continues with HEW device 104.1 and HEW device 104.2transmitting ACKs 310, 314 as shown by arrows 352.2, 352.1,respectively. In example embodiments, the HEW devices 104.1, 104.2 areconfigured to respond to acknowledge the MGMT frames 308.1, 308.2 in ascheduled MU PPDU. In example embodiments, the HEW devices 104.1 104.2are configured to respond to acknowledge the MGMT frames 308.1. 308.2 ina next scheduled MU PPDU. The method 300 may end.

FIG. 4 is a method 400 of acknowledgment in 802.11 in accordance withexample embodiments. Illustrated in FIG. 4 is time 466 along thehorizontal axis and along the vertical axis are. AP 102, HEW device104.1 HEW device 104.2, and legacy device 106.

The method 400 begins with HEW device 104.1 and HEW device 104.2transmitting management (MGMT) frames 410, 414 as shown by arrows 452.2,452.1, respectively. In example embodiments, the HEW devices 104.1,104.2 may transmit the MGMT frames 410, 414 in a TXOP 460 in which theAP 102 may have reserved time for the HEW devices 104.1, 104.2 totransmit the MGMT frames 410, 414. In example embodiments, the HEWdevices 104.1, 104.2 transmit packets before and/or after the MGMTframes 410, 414, respectively.

In example embodiments, the method 400 continues with the AP 102transmitting during a contention period 401 The method 400 continueswith the AP 102 transmitting (indicated by arrows 450.1, 450.2, 470) theSCH 402 to the HEW device 104.1, the HEW device 104.2, and the legacydevice 106, respectively.

In example embodiments, the SCH 402 may be a schedule as described forSCH 202 (FIG. 2). The legacy device 106 may set a NAV 471 based on alegacy header that indicates how long the wireless medium will be usedby the AP 102. The period of time the AP 102 has reserved may be calleda TXOP 460.

The method 400 continues with the AP 102 transmitting SIG 404 to the HEWdevice 104.1 and the HEW device 104.2 as shown by arrows 450.3, 450.4,respectively. The SIG 404 may be a signal as described for SIG 204 (FIG.2).

The method 400 continues with the AP 102 transmitting ACKs 408.1, 408.2of the MGMT frames 410, 414 as shown by arrows 450.5, 450.6,respectively. In example embodiments, the AP 102 may transmit additionalpackets either before or after the ACKs 408.1, 408.2. In exampleembodiments, the AP 102 is configured to acknowledge the MGMT frames410, 414 in a next scheduled PPDU. In example embodiments, the AP 102 isconfigured to acknowledge the MGMT frames 410, 414 in a next transmitopportunity of the AP 102. In example embodiments, the AP 102 isconfigured to acknowledge the MGMT frames 410, 414 before sending anydata packets (not illustrated). The method 400 may end.

FIG. 5 illustrates a schematic diagram of a packet, according to exampleembodiments. Illustrated in FIG. 5 is a packet 500 and field 502. Inexample embodiments, the packet 500 may be a new MAC management framefor multi-user operation that indicates an ACK policy. In exampleembodiments, the packet 500 may be an existing packet with a new ormodified field 502. For example, the packet 500 may be a beacon frame,probe response, signal frame, probe request, or another frame suitableto include field 502.

The field 502 may indicate how the HEW devices 104 and/or AP 102 are toacknowledge or block acknowledge frames.

In example embodiments, the field 502 indicates that the HEW device 104is to acknowledge or block acknowledge frames received in a nextscheduled MU PPDU. In example embodiments, the field 502 indicates thatthe HEW device 104 is to acknowledge or block acknowledge framesreceived in a next transmitted MU PPDU.

In example embodiments, the field 502 indicates that the HEW devices 104are to acknowledge or block acknowledge frames received in a nextscheduled packet. For example, in one embodiment, the field 502indicates that the HEW device 104 is to acknowledge frames received in anext packet. In example embodiments, the field 502 indicates that theHEW device 104 is to acknowledge a received management frame in a nexttransmission opportunity that the HEW device has. In exampleembodiments, the field 502 indicates that the HEW device 104 is toacknowledge a received management frame in a next MU PPDU transmitted bythe HEW device 104.

In example embodiments, the field 502 indicates that the HEW device 104is to acknowledge or block acknowledge frames in the currenttransmission opportunity, or if there is not a current transmissionopportunity, in a next transmission opportunity. For example, in exampleembodiments the HEW device 104 can acknowledge or block acknowledgeframes after sending data frames.

In example embodiments, the HEW device 104 acknowledging or blockacknowledging frames in a next scheduled transmission opportunity hasthe technical effect of reducing the use of the wireless medium becausethe HEW device 104 does not have to contend for the wireless medium inorder to acknowledge or block acknowledge frames.

In example embodiments, the HEW device 104 acknowledging or blockacknowledging frames in a next scheduled MU PPDU has the technicaleffect of reducing the use of the wireless medium because the HEW device104 does not have to contend for the wireless medium in order toacknowledge or block acknowledge frames and because the HEW device 104acknowledges or block acknowledges the received frames concurrently withone or more other HEW devices 104.

In example embodiments, the HEW device 104 acknowledging or blockacknowledging frames in a next scheduled MU PPDU has the technicaleffect of reducing the buffer sizes needed by the AP 102 and HEW device104 because the HEW device 104 and AP 102 will receive an acknowledge orblock acknowledgement sooner and thus will be able to free up bufferssooner.

FIG. 6 illustrates a HEW device 600 in accordance with some embodiments.HEW device 600 may be a HEW-compliant device that may be arranged tocommunicate with one or more other HEW devices, such as HEW devices 104(FIG. 1) or access point 102 (FIG. 1) as well as communicate with legacydevices 106 (FIG. 1). HEW devices 104 and legacy devices 106 may also bereferred to as HEW stations (STAs) and legacy STAs, respectively. HEWdevice 600 may be suitable for operating as access point 102 (FIG. 1) ora HEW device 104 (FIG. 1). In accordance with embodiments, HEW device600 may include, among other things, a transmit/receive element 601 (forexample an antenna), a transceiver 602, physical layer circuitry (PHY)604 and medium-access control layer circuitry (MAC) 606. PHY 604 and MAC606 may be HEW-compliant layers and may also be compliant with one ormore legacy IEEE 802.11 standards. MAC 606 may be arranged to configurePPDUs and arranged to transmit and receive PPDUs, among other things.HEW device 600 may also include other hardware circuitry 608 and memory610 configured to perform the various operations described herein. Thehardware circuitry 608 may be coupled to the transceiver 602, which maybe coupled to the transmit/receive element 601. While FIG. 6 depicts thehardware circuitry 608 and the transceiver 602 as separate components,the hardware circuitry 608 and the transceiver 602 may be integratedtogether in an electronic package or chip.

In example embodiments, the HEW device 104 is configured to perform oneor more of the functions and/or methods described herein such as themethods, apparatuses, and functions described in conjunction with FIGS.2 through 4, and in relation to packet 500.

The PHY 604 may be arranged to transmit the HEW PPDU. The PHY 604 mayinclude circuitry for modulation/demodulation,upconversion/downconversion, filtering, amplification, etc. In someembodiments, the hardware circuitry 608 may include one or moreprocessors. The hardware circuitry 608 may be configured to performfunctions based on instructions being stored in a RAM or ROM, or basedon special purpose circuitry. In sonic embodiments, the hardwarecircuitry 608 may be configured to perform one or more of the functionsdescribed herein for sending and receiving BARs and BAs.

In some embodiments, two or more antennas may be coupled to the PHY 604and arranged for sending and receiving signals including transmission ofthe HEW packets. The HEW device 600 may include a transceiver 602 totransmit and receive data such as HEW PPDU and packets that include anindication that the HEW device 600 should adapt the channel contentionsettings according to settings included in the packet. The memory 610may store information for configuring the other circuitry to performoperations for one or more of the functions and/or methods describedherein for acknowledgements and block acknowledgements such as themethods, apparatuses, and functions described in conjunction with FIGS.2 through 4, and in relation to packet 500.

In some embodiments, the HEW device 600 may be configured to communicateusing OFDM communication signals over a multicarrier communicationchannel. In some embodiments, HEW device 600 may be configured tocommunicate in accordance with one or more specific communicationstandards, such as the Institute of Electrical and Electronics Engineers(IEEE) standards including IEEE 802.11-2012, 802.11n-2009,802.11ac-2013, 802.11ax, standards and/or proposed specifications forWLANs, although the scope of the example embodiments is not limited inthis respect as they may also be suitable to transmit and/or receivecommunications in accordance with other techniques and standards. Insome embodiments, the HEW device 600 may use 4× symbol duration of 802.1in or 802.11ac.

In some embodiments, a HEW device 600 may be part of a portable wirelesscommunication device, such as a personal digital assistant (PDA), alaptop or portable computer with wireless communication capability, aweb tablet, a wireless telephone, a smartphone, a wireless headset, apager, an instant messaging device, a digital camera, an access point, atelevision, a medical device (e.g., a heart rate monitor, a bloodpressure monitor, etc.), an access point, a base station, atransmit/receive device for a wireless standard such as 802.11 or802.16, or other device that may receive and/or transmit informationwirelessly. In some embodiments, the mobile device may include one ormore of a keyboard, a display, a non-volatile memory port, multipleantennas, a graphics processor, an application processor, speakers, andother mobile device elements. The display may be an screen including atouch screen.

The transmit/receive element 601 may comprise one or more directional oromnidirectional antennas, including, for example, dipole antennas,monopole antennas, patch antennas, loop antennas, microstrip antennas orother types of antennas suitable for transmission of RF signals. In somemultiple-input multiple-output (MIMO) embodiments, the antennas may beeffectively separated to take advantage of spatial diversity and thedifferent channel characteristics that may result.

Although the device 600 is illustrated as having several separatefunctional elements, one or more of the functional elements may becombined and may be implemented by combinations of software-configuredelements, such as processing elements including digital signalprocessors (DSPs), and/or other hardware elements. For example, sonicelements may comprise one or more microprocessors, DSPs,field-programmable gate arrays (FPGAs), application specific integratedcircuits (ASICs), radio-frequency integrated circuits (RFICs) andcombinations of various hardware and logic circuitry for performing atleast the functions described herein. In some embodiments, thefunctional elements may refer to one or more processes operating on oneor more processing elements.

Example embodiments have the technical effect of increasing theefficiency of the wireless medium by acknowledging or blockacknowledging packets during a next transmission opportunity. In exampleembodiments, the HEW devices do not use the wireless medium forcontention, but rather wait for a next transmission opportunity beforeacknowledging or block acknowledging the packets.

Example embodiments have the technical effect of increasing theefficiency of the wireless medium by acknowledging management packetsduring a. next transmission opportunity. In example embodiments, the HEWdevices do not use the wireless medium for contention, but rather waitfor a next transmission opportunity before acknowledging the managementpackets.

Embodiments may be implemented in one or a combination of hardware,firmware and software. Embodiments may also be implemented asinstructions stored on a computer-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein. A computer-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a computer-readable storagedevice may include read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memorydevices, and other storage devices and media. Some embodiments mayinclude one or more processors and may be configured with instructionsstored on a computer-readable storage device.

The following examples pertain to further embodiments. Example 1 is ahigh-efficiency wireless local-area network (HEW) device. The HEW devicemay include circuitry configured to: receive one or more packets in atransmit opportunity (TXOP) from an access point (AP), wherein the oneor more packets indicate a schedule for the HEW device to transmit amulti-user physical-layer convergence procedure protocol data unit (MUPPDU); and transmit an acknowledgement of the one or more packets in theMU-PPDU.

In Example 2, the subject matter of Example 1 can optionally includewhere the acknowledgement is one from the foil owing group: a blockacknowledgement frame and acknowledgment frame.

In Example 2, the subject matter of Examples 1 and 2 can optionallyinclude where the circuitry is further to: transmit the acknowledgementframe and the block acknowledgement frame in a first scheduled PPDU.

In Example 4, the subject matter of any of Examples 1 through 3 canoptionally include where the one or more packets from the AP comprise amanagement frame, and wherein the circuitry is further configured to:transmit the acknowledgement of the management frame in a firstscheduled MU PPDU.

In Example 5, the subject matter of any of Examples 1-4 can optionallyinclude where the circuitry is further to: transmit one or more datapackets to the AP.

In Example 6, the subject matter of any of Examples 1-5 can optionallyinclude where the circuitry is further to: transmit the one or more datapackets to the AP in the TXOP after the transmission of theacknowledgement of the one or more packets from the AP.

In Example 7, the subject matter of Examples 5 or 6 can optionallyinclude where the circuitry is further to: receive an acknowledgementfrom the AP to the transmitted one or more data packets in a next TXOP.

In Example 8, the subject matter of any of Examples 1-7 can optionallyinclude where the schedule includes a bandwidth for the HEW device totransmit and an indication of a duration for how long the HEW device cantransmit.

In Example 9, the subject matter of any of Examples 1-8 can optionallyinclude where the circuitry is further to: wait a short interface spaceand then transmit the acknowledgement of the one or more packets in theTXOP.

In Example 10, the subject matter of any of Examples 1-9 can optionallyinclude where the circuitry is further to: receive an indication to usea new acknowledgement policy in at least one of a signal (SIG) field, ina media access control (MAC) field, in a beacon field, probe response,or a MAC management frame; and wherein the circuitry is furtherconfigured to: transmit an acknowledgement of the one or more packets inthe scheduled MU PPDU, if the indication of the new acknowledgementpolicy is received, otherwise transmit the acknowledgement of the one ormore packets according to a legacy protocol.

In Example 11, the subject matter of any of Examples 1-10 can optionallyinclude Where the one or more data packets are transmitted usingorthogonal frequency division multiple access (OFDMA) and multi-usermultiple-input multiple-output (MU-MIMO) and in accordance with802.11ax.

In Example 12, the subject matter of any of Examples 1-11 can optionallyinclude where the schedule includes a duration for the acknowledgment ofthe one or more packets.

In Example 13, the subject matter of any of Examples 1-12 can optionallyinclude memory and a transceiver coupled to the circuitry.

In Example 14, the subject matter of Example 13 can optionally includeone or more antennas coupled to the transceiver.

Example 15 is a method for acknowledgement performed on ahigh-efficiency wireless local-area network (HEW) device. The method mayinclude receiving one or more packets in a transmit opportunity (TXOP)from an access point (AP), wherein the one or more packets indicate aschedule for the HEW device to transmit a multi-user physical-layerconvergence procedure protocol data unit (MU PPDU); and transmitting anacknowledgement of the one or more packets in the MU PPDU.

In Example 16, the subject matter of Example 15 can optionally includewhere the acknowledgement is one from the following group: anacknowledgement frame and block acknowledgement frame.

In Example 17, the subject matter of Examples 15 and 16 can optionallyinclude where the transmitting the acknowledgement further comprises:transmitting the acknowledgement in a first scheduled PPDU.

In Example 18, the subject matter of Examples 16 or 17 can optionallyinclude where the schedule includes a duration for the acknowledgment ofthe one or more packets.

Example 19 is an access point (AP) including circuitry configured to:transmit one or more packets in a transmit opportunity (TXOP) to each ofone or more high-efficiency wireless local-area network (HEW) devices,wherein the one or more packets indicate a schedule for each of the oneor more HEW devices to transmit a multi-user physical-layer convergenceprocedure protocol data unit (MU PPDU); and receive an acknowledgementfrom each of the one or more HEW devices of the corresponding MU PPDU.

In Example 20, the subject matter of Example 19 can optionally includememory a transceiver coupled to the circuitry; and one or more antennascoupled to the transceiver.

In Example 21, the subject matter of Examples 19 and 20 can optionallyinclude where the acknowledgment is one from the following group:acknowledgement frame and block acknowledgement frame.

In Example 22, the subject matter of Example 21 can optionally includewhere the schedule includes a duration for each of the one or more HEWdevices to transmit the acknowledgment of the one or more packets.

In Example 23, the subject matter of any of Examples 19-23 canoptionally include Where the circuitry is further configured to: receivea management frame from at least one of the one or more HEW devices; andtransmit an acknowledgement of the management frame to each of the atleast one of the one or more HEW devices in a next scheduled MU-PPDU.

Example 24 is a non-transitory computer-readable storage medium thatstores instructions for execution by one or more processors to performoperations for high-efficiency wireless local-area network (HEW), wherethe instructions configure the one or more processors to: receive one ormore packets in a transmit opportunity (TXOP) from an access point (AP),wherein the one or more packets indicate a schedule for to transmit amulti-user physical-layer convergence procedure protocol data unit (MUPPDU); and transmit an acknowledgement of the one or more packets in thescheduled MU PPDU.

In Example 24, the subject matter of Example 25 can optionally includeherein the acknowledgement is one from the following group: anacknowledgment frame and block acknowledgment frame.

The Abstract is provided to comply with 37 C.F.R. Section 1.72(b)requiring an abstract that will allow the reader to ascertain the natureand gist of the technical disclosure. It is submitted with theunderstanding that it will not be used to limit or interpret the scopeor meaning of the claims. The following claims are hereby incorporatedinto the detailed description, with each claim standing on its own as aseparate embodiment.

1. (canceled)
 2. An apparatus of a high efficiency (HE) station, theapparatus comprising: memory; and processing circuitry coupled to thememory, the processing circuitry configured to: decode a multi-user (MU)physical-layer convergence procedure protocol data unit (MU PPDU) froman access point (AP), the MU PPDU comprising a first schedule, the firstschedule indicating a sub-channel for the HE station to receive data,the MU PPDU comprising the data, the data comprising one or morepackets, and a second schedule, the second schedule indicating asub-channel and length for transmission of an uplink (UL) MU PPDU to theAP; decode the data in accordance with the first schedule; and configurethe HE station to transmit the UL MU PPDU, the UL MU PPDU comprising anacknowledgement of the one or more packets, wherein the UL MU PPDU is tobe transmitted in accordance with the second schedule.
 3. The apparatusof claim 2, wherein the first schedule further indicates one or moreadditional sub-channels for one or more additional HE stations toreceive one or more additional data.
 4. The apparatus of claim 2,wherein the first schedule further comprises an indication of whetherthe data is to be received in accordance with MU multiple-inputmultiple-output (MU-MIMO), orthogonal frequency division multiple access(OFDMA), or both MU-MIMO and OFDMA.
 5. The apparatus of claim 2, whereinthe acknowledgement is a block acknowledgement.
 6. The apparatus ofclaim 2, the processing circuitry is configured to: decode anacknowledgement policy from the first schedule or the second schedule,wherein the acknowledgement policy indicates the one or more frames areto be acknowledged in the UL MU PPDU.
 7. The apparatus of claim 2,configure the station to transmit the UL MU PPDU a short interframespace (SIFS) after the MU PPDU is received.
 8. The apparatus of claim 2,wherein the second schedule further comprises an indication of whetherthe UL MU PPDU is to be transmitted in accordance with MU multiple-inputmultiple-output (MU-MIMO), orthogonal frequency division multiple access(OFDMA), or both MU-MIMO and OFDMA.
 9. The apparatus of claim 2, whereinthe processing circuitry is further configured to: configure the HEstation to transmit the UL MU PPDU in accordance with the secondschedule in a first scheduled UL transmission.
 10. The apparatus ofclaim 2, wherein the MU PPDU from the AP is to be received in atransmission opportunity (TXOP) and wherein the UL MU PPDU is to betransmitted in the TXOP.
 11. The apparatus of claim 2, wherein the MUPPDU further comprises a duration for the data.
 12. The apparatus ofclaim 2, wherein the processing circuitry is further to: decode apacket, the packet comprising an acknowledgement policy, wherein theacknowledgement policy indicates the one or more frames are to beacknowledged in the UL MU PPDU.
 13. The apparatus of claim 2, whereinthe memory is configured to store the MU PPDU and the UL MU PPDU. 14.The apparatus of claim 2 further comprising transceiver circuitrycoupled to the memory; and one or more antennas coupled to thetransceiver circuitry.
 15. A non-transitory computer-readable storagemedium that stores instructions for execution by one or more processors,the instructions to configure the one or more processors to cause anapparatus of a high-efficiency (HE) station to: decode a multi-user (MU)physical-layer convergence procedure protocol data unit (MU PPDU) froman access point (AP), the MU PPDU comprising a first schedule, the firstschedule indicating a sub-channel for the HE station to receive data,the MU PPDU comprising the data, the data comprising one or morepackets, and a second schedule, the second schedule indicating asub-channel and length for transmission of an uplink (UL) MU PPDU to theAP; decode the data in accordance with the first schedule; and configurethe HE station to transmit the UL MU PPDU, the UL MU PPDU comprising anacknowledgement of the one or more packets, wherein the UL MU PPDU is tobe transmitted in accordance with the second schedule.
 16. The apparatusof claim 15, wherein the first schedule further comprises one or moreadditional sub-channels for one or more additional HE stations toreceive one or more additional data.
 17. The apparatus of claim 15,wherein the first schedule further comprises an indication of whetherthe data is to be received in accordance with MU multiple-inputmultiple-output (MU-MIMO), orthogonal frequency division multiple access(OFDMA), or both MU-MIMO and OFDMA.
 18. A method performed by anapparatus of a high-efficiency (HE) station, the method comprising:decoding a multi-user (MU) physical-layer convergence procedure protocoldata unit (MU PPDU) from an access point (AP), the MU PPDU comprising afirst schedule, the first schedule indicating a sub-channel for the HEstation to receive data, the MU PPDU comprising the data, the datacomprising one or more packets, and a second schedule, the secondschedule indicating a sub-channel and length for transmission of anuplink (UL) MU PPDU to the AP; decoding the data in accordance with thefirst schedule; and configuring the HE station to transmit the UL MUPPDU, the UL MU PPDU comprising an acknowledgement of the one or morepackets, wherein the UL MU PPDU is to be transmitted in accordance withthe second schedule.
 19. The method of claim 18, wherein the firstschedule further comprises one or more additional sub-channels for oneor more additional HE stations to receive one or more additional data.20. An apparatus of a high-efficiency (HE) access point (AP), theapparatus comprising: memory, and processing circuitry configured to:encode a multi-user (MU) physical-layer convergence procedure protocoldata unit (MU PPDU), the MU PPDU comprising a first schedule, the firstschedule indicating sub-channels for HE stations to receive data, thedata comprising one or more packets, the MU PPDU comprising the data,the MU PPDU comprising a second schedule, the second schedule comprisinga length field indicating an uplink (UL) physical layer convergenceprocedure (PLCP) protocol data unit (PPDU) (UL-PPDU) response length,the second schedule further indicating second sub-channels for HEstations; configure the HE AP to transmit the MU PPDU; and decodeUL-PPDU responses from one or more HE stations of the HE stations,wherein a length of each of the UL-PPDU responses corresponds to theUL-PPDU response length, and wherein each of the UL-PPDU responsescomprises an acknowledgement of one or more packets.
 21. The apparatusof claim 20, wherein the acknowledgement of one or more packetsacknowledges the one or more packets being successfully received by acorresponding HE station of the one or more HE stations.
 22. Theapparatus of claim 20, wherein the acknowledgment of one or more packetsis a block acknowledgment of packets.
 23. The apparatus of claim 20,wherein the second schedule comprises an indication of how long otherstations should set a network allocation vector (NAV),
 24. The apparatusof claim 20, wherein one or more of the UL-PPDU responses comprises ULdata for the HE AP.
 25. The apparatus of claim 20, wherein theprocessing circuitry is further configured to: encode a packetcomprising an acknowledgment policy for the HE stations; and configurethe HE AP to transmit the packet, wherein the acknowledgment policyindicates that the HE stations are to acknowledge received packets in afirst packet to the HE AP.
 26. The apparatus of claim 20, the apparatusfurther comprising transceiver circuitry coupled to the memory; and, oneor more antennas coupled to the transceiver circuitry.